Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cabbdf5121c7ac7f03cf2fd173d5fb703a89a2342bb7f3d9606de12ba739330

Tx prefix hash: 56d268fe6108a02fd84d2a3efda08d264f252181be10b95bd695a7cfe3134ee2
Tx public key: 251b274238f9f3cba5899a0076d6ff0d0071068e1c590b13644d20f6c2e67230
Timestamp: 1718368974 Timestamp [UCT]: 2024-06-14 12:42:54 Age [y:d:h:m:s]: 00:334:20:05:10
Block: 1044044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239300 RingCT/type: yes/0
Extra: 01251b274238f9f3cba5899a0076d6ff0d0071068e1c590b13644d20f6c2e672300211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3daf8b4a6009259d474c0242bf76d6c036f267e22e6c374f1efa4370ce31b274 0.600000000000 1513241 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": 1044054, "vin": [ { "gen": { "height": 1044044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3daf8b4a6009259d474c0242bf76d6c036f267e22e6c374f1efa4370ce31b274" } } ], "extra": [ 1, 37, 27, 39, 66, 56, 249, 243, 203, 165, 137, 154, 0, 118, 214, 255, 13, 0, 113, 6, 142, 28, 89, 11, 19, 100, 77, 32, 246, 194, 230, 114, 48, 2, 17, 0, 0, 0, 3, 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