Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ec8176f45e560f716ed1a516debf408391fd5c17af6de539cbc84038baa19bf

Tx prefix hash: 52f900bdb59f0405ca93b11375d894564c7946fbe609b94ae180e5da20c63d96
Tx public key: 3a1cd03629afceb60dc4c906aee5b1fbc5256ed3d0e0f806cebed80ceb97f380
Timestamp: 1574664647 Timestamp [UCT]: 2019-11-25 06:50:47 Age [y:d:h:m:s]: 05:051:03:48:12
Block: 16986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1179413 RingCT/type: yes/0
Extra: 013a1cd03629afceb60dc4c906aee5b1fbc5256ed3d0e0f806cebed80ceb97f380021100000001f95225a5000000000000000000

1 output(s) for total of 539.161921018000 dcy

stealth address amount amount idx
00: 7769009d10a1b5a08a1e4d522083b69d351f52280787a313ca4a86736e152c4c 539.161921018000 24232 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": 16996, "vin": [ { "gen": { "height": 16986 } } ], "vout": [ { "amount": 539161921018, "target": { "key": "7769009d10a1b5a08a1e4d522083b69d351f52280787a313ca4a86736e152c4c" } } ], "extra": [ 1, 58, 28, 208, 54, 41, 175, 206, 182, 13, 196, 201, 6, 174, 229, 177, 251, 197, 37, 110, 211, 208, 224, 248, 6, 206, 190, 216, 12, 235, 151, 243, 128, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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