Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e62a646fac00a1cf70f963448b1b33553581e4c8755d5d622cc6fb48230a0e76

Tx prefix hash: be60ccb94f45709337243876cea65f80d7927b80bda0d9558f1dcd1d647ca3a4
Tx public key: ad2b63df9aad49ed77a0ee84b4d2e7ab7e32d3d5aa48cb81868804cfb9ca8f1f
Timestamp: 1617104354 Timestamp [UCT]: 2021-03-30 11:39:14 Age [y:d:h:m:s]: 03:291:05:51:51
Block: 229679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 967641 RingCT/type: yes/0
Extra: 01ad2b63df9aad49ed77a0ee84b4d2e7ab7e32d3d5aa48cb81868804cfb9ca8f1f0211000000069c1fbdcc000000000000000000

1 output(s) for total of 106.409085496000 dcy

stealth address amount amount idx
00: bd3e1832da5f2f1022286cf430e224623b6ccea154c58bfbe4b7ee14dd81d2b9 106.409085496000 476641 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": 229689, "vin": [ { "gen": { "height": 229679 } } ], "vout": [ { "amount": 106409085496, "target": { "key": "bd3e1832da5f2f1022286cf430e224623b6ccea154c58bfbe4b7ee14dd81d2b9" } } ], "extra": [ 1, 173, 43, 99, 223, 154, 173, 73, 237, 119, 160, 238, 132, 180, 210, 231, 171, 126, 50, 211, 213, 170, 72, 203, 129, 134, 136, 4, 207, 185, 202, 143, 31, 2, 17, 0, 0, 0, 6, 156, 31, 189, 204, 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