Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a91b3052b54ebe88e3c4242a1bbd0f2c8483b1306f7c7cf448a47320e4c0ef19

Tx prefix hash: a60630a1997814678492c1636eacf7ef418a454ccea6b070aa210236353ae7d6
Tx public key: cea5e5e429946451d193636b36ec6dcbe0ed6dfb8eb4bdfd1d50dc5836667fea
Timestamp: 1580567859 Timestamp [UCT]: 2020-02-01 14:37:39 Age [y:d:h:m:s]: 05:100:06:43:40
Block: 56530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1223606 RingCT/type: yes/0
Extra: 01cea5e5e429946451d193636b36ec6dcbe0ed6dfb8eb4bdfd1d50dc5836667fea02110000000217786bcf000000000000000000

1 output(s) for total of 398.743362368000 dcy

stealth address amount amount idx
00: 8b113478074b5bb741d87e3b35bf8f467a076d2f181958f17e3d57b2311602b1 398.743362368000 104267 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": 56540, "vin": [ { "gen": { "height": 56530 } } ], "vout": [ { "amount": 398743362368, "target": { "key": "8b113478074b5bb741d87e3b35bf8f467a076d2f181958f17e3d57b2311602b1" } } ], "extra": [ 1, 206, 165, 229, 228, 41, 148, 100, 81, 209, 147, 99, 107, 54, 236, 109, 203, 224, 237, 109, 251, 142, 180, 189, 253, 29, 80, 220, 88, 54, 102, 127, 234, 2, 17, 0, 0, 0, 2, 23, 120, 107, 207, 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