Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c141265f310e94f2ddb643c832ebe36118d252ada638db61ad97b7f32fe74c8

Tx prefix hash: 14e9d3871764e38062b280580f1ff71e9644ef2e345461f31d970df4e99095e0
Tx public key: cbe9a2dddc5ec7ca1f0eebb34e2a1a4db19959f16ddcab4bfe070c5f433caa62
Timestamp: 1729661772 Timestamp [UCT]: 2024-10-23 05:36:12 Age [y:d:h:m:s]: 00:032:02:30:38
Block: 1137626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22930 RingCT/type: yes/0
Extra: 01cbe9a2dddc5ec7ca1f0eebb34e2a1a4db19959f16ddcab4bfe070c5f433caa620211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc7315f529ca5b996a122258fc68db65c804ce9b45f459186d3ab5dcf65e6eaa 0.600000000000 1621151 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": 1137636, "vin": [ { "gen": { "height": 1137626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc7315f529ca5b996a122258fc68db65c804ce9b45f459186d3ab5dcf65e6eaa" } } ], "extra": [ 1, 203, 233, 162, 221, 220, 94, 199, 202, 31, 14, 235, 179, 78, 42, 26, 77, 177, 153, 89, 241, 109, 220, 171, 75, 254, 7, 12, 95, 67, 60, 170, 98, 2, 17, 0, 0, 0, 1, 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