Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 312b6383030719f1d82e0bf16d684ee724e33a43d373418436397133ffe2fe0e

Tx prefix hash: a9b948146a90b4f55c8e266ac6d41160e694eb3e9dda648ee8df9d8bb8cd4feb
Tx public key: 02951b2e1723433fd6f6dc0c3afe644cf59bd7ff773ce388f7a4a3e1f66731ea
Timestamp: 1735292380 Timestamp [UCT]: 2024-12-27 09:39:40 Age [y:d:h:m:s]: 00:084:15:39:36
Block: 1184203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60293 RingCT/type: yes/0
Extra: 0102951b2e1723433fd6f6dc0c3afe644cf59bd7ff773ce388f7a4a3e1f66731ea0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa9cbc37ae0a58e2efcbacdaf6d207b1c0a0a6eba553f67edc237dd208e96b23 0.600000000000 1670658 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": 1184213, "vin": [ { "gen": { "height": 1184203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa9cbc37ae0a58e2efcbacdaf6d207b1c0a0a6eba553f67edc237dd208e96b23" } } ], "extra": [ 1, 2, 149, 27, 46, 23, 35, 67, 63, 214, 246, 220, 12, 58, 254, 100, 76, 245, 155, 215, 255, 119, 60, 227, 136, 247, 164, 163, 225, 246, 103, 49, 234, 2, 17, 0, 0, 0, 3, 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