Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef7a2ce7591f53d0d7b4d6095916933024a55557f5105dfa7ee80567a16fc077

Tx prefix hash: 3f545ce0f34e280694d077ed7473dc2d065e5be498aed1822945589432ff7a33
Tx public key: 8fdd18b079b3bd9112f6fc7d6e3bcd6b3d84038680fff93f831a434326ea0f09
Timestamp: 1729708687 Timestamp [UCT]: 2024-10-23 18:38:07 Age [y:d:h:m:s]: 00:186:13:55:56
Block: 1138014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133167 RingCT/type: yes/0
Extra: 018fdd18b079b3bd9112f6fc7d6e3bcd6b3d84038680fff93f831a434326ea0f090211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 779f0de624596faaf85ac48b3bfce199cddb84a6ec551f056a30bc02b4964da2 0.600000000000 1621613 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": 1138024, "vin": [ { "gen": { "height": 1138014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "779f0de624596faaf85ac48b3bfce199cddb84a6ec551f056a30bc02b4964da2" } } ], "extra": [ 1, 143, 221, 24, 176, 121, 179, 189, 145, 18, 246, 252, 125, 110, 59, 205, 107, 61, 132, 3, 134, 128, 255, 249, 63, 131, 26, 67, 67, 38, 234, 15, 9, 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