Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 384b87a8b0e620d40017e299f8895b663d361ba0e76bc575ada0d8b13fa3d49b

Tx prefix hash: 8e0b780dec4c54f4bc70c4a5f2ee5b24b9128ddf510383f43922fe2ac72d0303
Tx public key: 28ca9883b243d322a2959f0ac848844a78a93e9abb179724a4e76502d22c2b66
Timestamp: 1581202270 Timestamp [UCT]: 2020-02-08 22:51:10 Age [y:d:h:m:s]: 04:322:10:39:53
Block: 60937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122565 RingCT/type: yes/0
Extra: 0128ca9883b243d322a2959f0ac848844a78a93e9abb179724a4e76502d22c2b660211000000128a2ee0d9000000000000000000

1 output(s) for total of 385.559350326000 dcy

stealth address amount amount idx
00: 48cab2d778a14059bdd85b47839419f4e6d465ac337ff0ce783923aa8026ec95 385.559350326000 112324 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": 60947, "vin": [ { "gen": { "height": 60937 } } ], "vout": [ { "amount": 385559350326, "target": { "key": "48cab2d778a14059bdd85b47839419f4e6d465ac337ff0ce783923aa8026ec95" } } ], "extra": [ 1, 40, 202, 152, 131, 178, 67, 211, 34, 162, 149, 159, 10, 200, 72, 132, 74, 120, 169, 62, 154, 187, 23, 151, 36, 164, 231, 101, 2, 210, 44, 43, 102, 2, 17, 0, 0, 0, 18, 138, 46, 224, 217, 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