Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 416e16f4e6262f379a9d63d80101043f8bb91f29fbcfb072dcd454cfa7e2985b

Tx prefix hash: 4b580441ec2e49891e73f39ec0dd057873e57e067a200e99411761f0455c855f
Tx public key: cc52cfad7be2b0c1d0e980ba83f3887f66a263efa7b97ed7246fe798ca5964b8
Timestamp: 1712974717 Timestamp [UCT]: 2024-04-13 02:18:37 Age [y:d:h:m:s]: 00:361:09:27:24
Block: 999290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258394 RingCT/type: yes/0
Extra: 01cc52cfad7be2b0c1d0e980ba83f3887f66a263efa7b97ed7246fe798ca5964b80211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17e0e64331155102c19c07abc799f97b184f7d5995443ad74b2f9cb269e70136 0.600000000000 1459768 of 15

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": 999300, "vin": [ { "gen": { "height": 999290 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17e0e64331155102c19c07abc799f97b184f7d5995443ad74b2f9cb269e70136" } } ], "extra": [ 1, 204, 82, 207, 173, 123, 226, 176, 193, 208, 233, 128, 186, 131, 243, 136, 127, 102, 162, 99, 239, 167, 185, 126, 215, 36, 111, 231, 152, 202, 89, 100, 184, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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