Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36e314dcfd7c41137298fd497b77cc8a4b3f9cbf3ed1e01ea236d0b2d06b5c2a

Tx prefix hash: bca324041cdd289af94efcc9ec272b3ce431d32296d2f48759e58cdbf348bcba
Tx public key: 6fb70f782e384752bdacae599c1e458adf993b5a19488766e8dc5f1ba4caa2af
Timestamp: 1695175087 Timestamp [UCT]: 2023-09-20 01:58:07 Age [y:d:h:m:s]: 01:195:13:12:26
Block: 851937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400839 RingCT/type: yes/0
Extra: 016fb70f782e384752bdacae599c1e458adf993b5a19488766e8dc5f1ba4caa2af021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.922952004000 dcy

stealth address amount amount idx
00: 2e1f34946a50a5499a552919ec620250945e5d325eb73cc32eb28b506de1fb2c 0.922952004000 1305749 of 0

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": 851947, "vin": [ { "gen": { "height": 851937 } } ], "vout": [ { "amount": 922952004, "target": { "key": "2e1f34946a50a5499a552919ec620250945e5d325eb73cc32eb28b506de1fb2c" } } ], "extra": [ 1, 111, 183, 15, 120, 46, 56, 71, 82, 189, 172, 174, 89, 156, 30, 69, 138, 223, 153, 59, 90, 25, 72, 135, 102, 232, 220, 95, 27, 164, 202, 162, 175, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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