Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5581feb20aa8d1183a0bc7142d24e7e8ab024ffbea9f4a473960cc0ed37a21f9

Tx prefix hash: 6b4df018d90ffe05b916483742fd4ea41b6f6bdf6ca92d761256753a5fa11dcc
Tx public key: 3d927e1cde75920e1be4b0295de5bca7591d4fe0093fd1b1f6b0833d6da21a8d
Timestamp: 1730981717 Timestamp [UCT]: 2024-11-07 12:15:17 Age [y:d:h:m:s]: 00:016:19:18:49
Block: 1148512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12029 RingCT/type: yes/0
Extra: 013d927e1cde75920e1be4b0295de5bca7591d4fe0093fd1b1f6b0833d6da21a8d0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c64ccf1067311a1b404903d3253c08c78f970c245862636baaa72fa98d5ae8c 0.600000000000 1633379 of 15

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": 1148522, "vin": [ { "gen": { "height": 1148512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c64ccf1067311a1b404903d3253c08c78f970c245862636baaa72fa98d5ae8c" } } ], "extra": [ 1, 61, 146, 126, 28, 222, 117, 146, 14, 27, 228, 176, 41, 93, 229, 188, 167, 89, 29, 79, 224, 9, 63, 209, 177, 246, 176, 131, 61, 109, 162, 26, 141, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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