Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c671fb24166c5f891f300c126c8ed5f6fdc7f61dad43caf832b54185c31a54d

Tx prefix hash: 986f1b78ac4b1cf465d169e9c9dc6999a57699c76db4912b948f68bd7e3d527e
Tx public key: 58c5e1bf445782014022bd949a3a0eec64d25cbdbdeb2abcdebf96a11bd838da
Timestamp: 1736670333 Timestamp [UCT]: 2025-01-12 08:25:33 Age [y:d:h:m:s]: 00:064:02:49:03
Block: 1195619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45616 RingCT/type: yes/0
Extra: 0158c5e1bf445782014022bd949a3a0eec64d25cbdbdeb2abcdebf96a11bd838da0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7c2ab8218efe89094a4ccf7455aeee9cc5e9d863b47844dc1b1c9f0d94641c0 0.600000000000 1682210 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": 1195629, "vin": [ { "gen": { "height": 1195619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7c2ab8218efe89094a4ccf7455aeee9cc5e9d863b47844dc1b1c9f0d94641c0" } } ], "extra": [ 1, 88, 197, 225, 191, 68, 87, 130, 1, 64, 34, 189, 148, 154, 58, 14, 236, 100, 210, 92, 189, 189, 235, 42, 188, 222, 191, 150, 161, 27, 216, 56, 218, 2, 17, 0, 0, 0, 2, 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