Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: fa1d57cdcb1ce94c52b56c70cb7bb275d89c1bf2dd86c439720b60527dd5881b

Tx prefix hash: 8defa8b28d4ddc64410b15802826f495d1efbc878bd11892976aaf614490cdfb
Tx public key: 6de4ffe4ac8a1da4a693603993e5fd7d0937269ca0d79de3d0895c911abc85cc
Timestamp: 1610041484 Timestamp [UCT]: 2021-01-07 17:44:44 Age [y:d:h:m:s]: 03:353:16:00:27
Block: 175916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1007593 RingCT/type: yes/0
Extra: 016de4ffe4ac8a1da4a693603993e5fd7d0937269ca0d79de3d0895c911abc85cc0211000000264ea414e5000000000000000000

1 output(s) for total of 160.368077508000 dcy

stealth address amount amount idx
00: 05c9aa082ff5496d3bf2d7cf6c7bedcf8bf72505072019ab0dca3de2c5d0770d 160.368077508000 336488 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 175926, "vin": [ { "gen": { "height": 175916 } } ], "vout": [ { "amount": 160368077508, "target": { "key": "05c9aa082ff5496d3bf2d7cf6c7bedcf8bf72505072019ab0dca3de2c5d0770d" } } ], "extra": [ 1, 109, 228, 255, 228, 172, 138, 29, 164, 166, 147, 96, 57, 147, 229, 253, 125, 9, 55, 38, 156, 160, 215, 157, 227, 208, 137, 92, 145, 26, 188, 133, 204, 2, 17, 0, 0, 0, 38, 78, 164, 20, 229, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8