Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab0cc451766e0b5812ad733423ed6c5a227be3d326f2a82899718614abefeab9

Tx prefix hash: 722e021168d44be417fba7c59c39bd5692f55e8e788d94ba3d8fa9adcb43bfbb
Tx public key: c3b9a49841ce831b9cd51807b5778d60cd5a3d6dbf4c10ec900f0057a62e39c5
Timestamp: 1590590287 Timestamp [UCT]: 2020-05-27 14:38:07 Age [y:d:h:m:s]: 04:213:05:53:13
Block: 103715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1079393 RingCT/type: yes/0
Extra: 01c3b9a49841ce831b9cd51807b5778d60cd5a3d6dbf4c10ec900f0057a62e39c502110000000c4ac5aa02000000000000000000

1 output(s) for total of 278.195376626000 dcy

stealth address amount amount idx
00: 5c7172ad54b8a1482bc0bbb9d1c1dfda4f4c9b9ef641d62954f6908f12146e99 278.195376626000 181890 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": 103725, "vin": [ { "gen": { "height": 103715 } } ], "vout": [ { "amount": 278195376626, "target": { "key": "5c7172ad54b8a1482bc0bbb9d1c1dfda4f4c9b9ef641d62954f6908f12146e99" } } ], "extra": [ 1, 195, 185, 164, 152, 65, 206, 131, 27, 156, 213, 24, 7, 181, 119, 141, 96, 205, 90, 61, 109, 191, 76, 16, 236, 144, 15, 0, 87, 166, 46, 57, 197, 2, 17, 0, 0, 0, 12, 74, 197, 170, 2, 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