Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 631486d317a6af9a9e55ddf9fce87fc4268d7398a04ceb06490e4b0e25a4e8dd

Tx prefix hash: 4644ff19ea1d2501840e902dd8d9c0239be897306302321f794c16348baa6719
Tx public key: fd8cd64dbafba8bdb516842795e3c7ac67fa5eb3cb83ba5a28c884fdf892d98a
Timestamp: 1721071792 Timestamp [UCT]: 2024-07-15 19:29:52 Age [y:d:h:m:s]: 00:256:15:32:45
Block: 1066459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183336 RingCT/type: yes/0
Extra: 01fd8cd64dbafba8bdb516842795e3c7ac67fa5eb3cb83ba5a28c884fdf892d98a021100000007e914dd15000000000000000000

1 output(s) for total of 0.615600000000 dcy

stealth address amount amount idx
00: 52dcd36f6199c57704253ebfb4752adc3ef1573dc0a6f18638b201e10c51340e 0.615600000000 1537062 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": 1066469, "vin": [ { "gen": { "height": 1066459 } } ], "vout": [ { "amount": 615600000, "target": { "key": "52dcd36f6199c57704253ebfb4752adc3ef1573dc0a6f18638b201e10c51340e" } } ], "extra": [ 1, 253, 140, 214, 77, 186, 251, 168, 189, 181, 22, 132, 39, 149, 227, 199, 172, 103, 250, 94, 179, 203, 131, 186, 90, 40, 200, 132, 253, 248, 146, 217, 138, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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