Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2490100257d3cf0a4aa95741e99c26f4a192f3f2c9b80fa9e1e4bee3d1c12817

Tx prefix hash: bd3b29bf282ca50c15d6cd97f8ded1571c0908f9a24e8e65a8a8f9acd20578fc
Tx public key: e36fe5d7fa6f17d3009bd7722e25d3a2ac5fad3d055754f614b0961c6d5f65d4
Timestamp: 1574348059 Timestamp [UCT]: 2019-11-21 14:54:19 Age [y:d:h:m:s]: 05:043:00:20:30
Block: 13727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1174232 RingCT/type: yes/0
Extra: 01e36fe5d7fa6f17d3009bd7722e25d3a2ac5fad3d055754f614b0961c6d5f65d402110000000386c1f348000000000000000000

1 output(s) for total of 552.747844057000 dcy

stealth address amount amount idx
00: 8621cce7afae01a08de76cf622fd4c82fbb149d176726bdbfa812a751e70e46f 552.747844057000 16596 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": 13737, "vin": [ { "gen": { "height": 13727 } } ], "vout": [ { "amount": 552747844057, "target": { "key": "8621cce7afae01a08de76cf622fd4c82fbb149d176726bdbfa812a751e70e46f" } } ], "extra": [ 1, 227, 111, 229, 215, 250, 111, 23, 211, 0, 155, 215, 114, 46, 37, 211, 162, 172, 95, 173, 61, 5, 87, 84, 246, 20, 176, 150, 28, 109, 95, 101, 212, 2, 17, 0, 0, 0, 3, 134, 193, 243, 72, 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