Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51bfba9ef67955de97d367f2cfc0dbd70bb6fed005c9b61282e879c4837010a0

Tx prefix hash: fd9403397b5dfa10592691d56b76485bda68dcbeac0954358d96ab57c7c52332
Tx public key: 833a4e4323aa42cefd27535f2f5274c4b4aa188b9b211f793deb44eba2167e7c
Timestamp: 1733596009 Timestamp [UCT]: 2024-12-07 18:26:49 Age [y:d:h:m:s]: 00:123:16:25:45
Block: 1170171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88197 RingCT/type: yes/0
Extra: 01833a4e4323aa42cefd27535f2f5274c4b4aa188b9b211f793deb44eba2167e7c0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6ad7a9917fa667d0ec74dddee4ed4f10d905496fa589d7d48f18d412e1394db 0.600000000000 1655900 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": 1170181, "vin": [ { "gen": { "height": 1170171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6ad7a9917fa667d0ec74dddee4ed4f10d905496fa589d7d48f18d412e1394db" } } ], "extra": [ 1, 131, 58, 78, 67, 35, 170, 66, 206, 253, 39, 83, 95, 47, 82, 116, 196, 180, 170, 24, 139, 155, 33, 31, 121, 61, 235, 68, 235, 162, 22, 126, 124, 2, 17, 0, 0, 0, 4, 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