Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6957222a3ddd6f3362fd073386d9705ead546ddf4146e96383565260f15d13d2

Tx prefix hash: 4c4d0f0286901b50e2757f10adc7ebae455b74d0163d94a6c87952c9e193d99b
Tx public key: c558b072ff502e0a97e9a3212d25801b8ab51b613c6e85942c355e5497df7e0f
Timestamp: 1721105580 Timestamp [UCT]: 2024-07-16 04:53:00 Age [y:d:h:m:s]: 00:261:20:56:32
Block: 1066734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187061 RingCT/type: yes/0
Extra: 01c558b072ff502e0a97e9a3212d25801b8ab51b613c6e85942c355e5497df7e0f02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f2c80fd9b01ff9a2ecfc4ea51f216289b7a7f3ea0b0eea59c62f772b3da77c4 0.600000000000 1537401 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": 1066744, "vin": [ { "gen": { "height": 1066734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f2c80fd9b01ff9a2ecfc4ea51f216289b7a7f3ea0b0eea59c62f772b3da77c4" } } ], "extra": [ 1, 197, 88, 176, 114, 255, 80, 46, 10, 151, 233, 163, 33, 45, 37, 128, 27, 138, 181, 27, 97, 60, 110, 133, 148, 44, 53, 94, 84, 151, 223, 126, 15, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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