Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db2e7554ce8eac2d23a14cd2e9cab2ecefcaee4090b4074e669d7e8870677af2

Tx prefix hash: b7768de7d3803dcab5daecf5b0335d5b76f0d643f513c0b3075b762ce3fbdfa8
Tx public key: a0e56e5578d659102057edd6eab36aa92bb7eb7ad0859da791293180dfc979b5
Timestamp: 1582284196 Timestamp [UCT]: 2020-02-21 11:23:16 Age [y:d:h:m:s]: 04:280:06:51:35
Block: 69404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1092882 RingCT/type: yes/0
Extra: 01a0e56e5578d659102057edd6eab36aa92bb7eb7ad0859da791293180dfc979b50211000000074943cd9f000000000000000000

1 output(s) for total of 361.465232981000 dcy

stealth address amount amount idx
00: 9a565ee4e6c3789cba029e6a7b29b802c285405329c39be33d78c8455136c1d3 361.465232981000 128012 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": 69414, "vin": [ { "gen": { "height": 69404 } } ], "vout": [ { "amount": 361465232981, "target": { "key": "9a565ee4e6c3789cba029e6a7b29b802c285405329c39be33d78c8455136c1d3" } } ], "extra": [ 1, 160, 229, 110, 85, 120, 214, 89, 16, 32, 87, 237, 214, 234, 179, 106, 169, 43, 183, 235, 122, 208, 133, 157, 167, 145, 41, 49, 128, 223, 201, 121, 181, 2, 17, 0, 0, 0, 7, 73, 67, 205, 159, 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