Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 640b1f2c2cc74058cb298e95422d15c32e18b5a892de70c3cd9d4ed6a5a1a798

Tx prefix hash: 44912ede1974c15a6d8bcbd89b5edb70b87138d94ba7944fdc8124affe4d5ed2
Tx public key: e54df7711eabfae8a089be4b74a238e704d1f90c6fc1e886c5ed36341609d98b
Timestamp: 1583747784 Timestamp [UCT]: 2020-03-09 09:56:24 Age [y:d:h:m:s]: 04:311:20:41:23
Block: 78935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118061 RingCT/type: yes/0
Extra: 01e54df7711eabfae8a089be4b74a238e704d1f90c6fc1e886c5ed36341609d98b021100000001203e3db0000000000000000000

1 output(s) for total of 336.090602337000 dcy

stealth address amount amount idx
00: 0b182a21bb9930478a8aa6893e08ef74d7635919d748a9cbc33dc54262ce7c89 336.090602337000 144621 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": 78945, "vin": [ { "gen": { "height": 78935 } } ], "vout": [ { "amount": 336090602337, "target": { "key": "0b182a21bb9930478a8aa6893e08ef74d7635919d748a9cbc33dc54262ce7c89" } } ], "extra": [ 1, 229, 77, 247, 113, 30, 171, 250, 232, 160, 137, 190, 75, 116, 162, 56, 231, 4, 209, 249, 12, 111, 193, 232, 134, 197, 237, 54, 52, 22, 9, 217, 139, 2, 17, 0, 0, 0, 1, 32, 62, 61, 176, 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