Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e33be63053e72ce2d72b6f9b9fda16c49a0bfb9e960010ab4444b28538e0e8f

Tx prefix hash: 98e699f436b494fe76c914a84abfba38f9a7c0a28b4a868569f3a3e297ea0f83
Tx public key: 41186ada76ab2c246aee64fdf375403d9296f1ff5b04500716b194af410ff802
Timestamp: 1734126746 Timestamp [UCT]: 2024-12-13 21:52:26 Age [y:d:h:m:s]: 00:108:23:25:46
Block: 1174579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77648 RingCT/type: yes/0
Extra: 0141186ada76ab2c246aee64fdf375403d9296f1ff5b04500716b194af410ff8020211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf33dfc0eedba54685bb8bcc22181788551ef3b01765a8bf535f855931d1b5a0 0.600000000000 1660748 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": 1174589, "vin": [ { "gen": { "height": 1174579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf33dfc0eedba54685bb8bcc22181788551ef3b01765a8bf535f855931d1b5a0" } } ], "extra": [ 1, 65, 24, 106, 218, 118, 171, 44, 36, 106, 238, 100, 253, 243, 117, 64, 61, 146, 150, 241, 255, 91, 4, 80, 7, 22, 177, 148, 175, 65, 15, 248, 2, 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