Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5e4ae899546a018da433f5c122c25e1d62f3c133fdde88cd5d0600f7daa3a38

Tx prefix hash: ea202e57531a047de2ccf482aa52e74add32d1a7d9d8e0124a17d88595a25a66
Tx public key: 9159cbf4a42964876fd59529fe9d9cda11d8e3e9f9bed28d1e2bb9ab5b27e13a
Timestamp: 1625594834 Timestamp [UCT]: 2021-07-06 18:07:14 Age [y:d:h:m:s]: 04:118:02:18:48
Block: 289337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1112832 RingCT/type: yes/0
Extra: 019159cbf4a42964876fd59529fe9d9cda11d8e3e9f9bed28d1e2bb9ab5b27e13a02110000001de2af105e000000000000000000

1 output(s) for total of 67.500488467000 dcy

stealth address amount amount idx
00: fe040e863fad2cc7dee4249122b324e03436c365e4f67971eba37287a3da8ce8 67.500488467000 605995 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": 289347, "vin": [ { "gen": { "height": 289337 } } ], "vout": [ { "amount": 67500488467, "target": { "key": "fe040e863fad2cc7dee4249122b324e03436c365e4f67971eba37287a3da8ce8" } } ], "extra": [ 1, 145, 89, 203, 244, 164, 41, 100, 135, 111, 213, 149, 41, 254, 157, 156, 218, 17, 216, 227, 233, 249, 190, 210, 141, 30, 43, 185, 171, 91, 39, 225, 58, 2, 17, 0, 0, 0, 29, 226, 175, 16, 94, 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