Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90b1f9b44c49d6d4151847a9c23d59db3f42ec570127ff97ca19aac8127e187a

Tx prefix hash: 781a8ca641d56f39e0514624cbb7b2c0031d3f30aa38452b40482361d2186eee
Tx public key: e036a896470d5e637b23d847c19299f326e73e68ef76ae6297b81a9421aa629a
Timestamp: 1581945155 Timestamp [UCT]: 2020-02-17 13:12:35 Age [y:d:h:m:s]: 05:103:02:17:43
Block: 66617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1226950 RingCT/type: yes/0
Extra: 01e036a896470d5e637b23d847c19299f326e73e68ef76ae6297b81a9421aa629a02110000000256c366d3000000000000000000

1 output(s) for total of 369.207941217000 dcy

stealth address amount amount idx
00: 826c26a8eca59317b3af43b7a9f94825d3c3c64237c1bc1c04907a3f1a1a671c 369.207941217000 122750 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": 66627, "vin": [ { "gen": { "height": 66617 } } ], "vout": [ { "amount": 369207941217, "target": { "key": "826c26a8eca59317b3af43b7a9f94825d3c3c64237c1bc1c04907a3f1a1a671c" } } ], "extra": [ 1, 224, 54, 168, 150, 71, 13, 94, 99, 123, 35, 216, 71, 193, 146, 153, 243, 38, 231, 62, 104, 239, 118, 174, 98, 151, 184, 26, 148, 33, 170, 98, 154, 2, 17, 0, 0, 0, 2, 86, 195, 102, 211, 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