Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b20e45e9b5cba670a9d49e5f0496d244bd703a7e8f05e408e6997ffae4a8ea1f

Tx prefix hash: 75b055821862061739475992416a78711671fc4ff4b044a7db336e7b075e8240
Tx public key: 0f49cb5e58545cb45311169648c9bd6d93d6735ca4e4546ce1caa3390e6befce
Timestamp: 1648467951 Timestamp [UCT]: 2022-03-28 11:45:51 Age [y:d:h:m:s]: 03:217:22:05:00
Block: 468160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 933694 RingCT/type: yes/0
Extra: 010f49cb5e58545cb45311169648c9bd6d93d6735ca4e4546ce1caa3390e6befce0211000000075eb576c5000000000000000000

1 output(s) for total of 17.250108446000 dcy

stealth address amount amount idx
00: 00668a82986374d47f455421d8784be24f18e6a19906ccd1e8194497ff4b8ad2 17.250108446000 886814 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": 468170, "vin": [ { "gen": { "height": 468160 } } ], "vout": [ { "amount": 17250108446, "target": { "key": "00668a82986374d47f455421d8784be24f18e6a19906ccd1e8194497ff4b8ad2" } } ], "extra": [ 1, 15, 73, 203, 94, 88, 84, 92, 180, 83, 17, 22, 150, 72, 201, 189, 109, 147, 214, 115, 92, 164, 228, 84, 108, 225, 202, 163, 57, 14, 107, 239, 206, 2, 17, 0, 0, 0, 7, 94, 181, 118, 197, 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