Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8000de6dcace754db95b481eb2fdf6e0b5761a966a4ed9792e057b1b79e2b191

Tx prefix hash: 3bdb401d9d9f7a8fea1754f07e7accd510af73ab8d0f275a7859a0760d6a8d8c
Tx public key: b440e6b4fde6bc1f6d8bd804619f88d68c8a8a52ceec8da4bb7a914afc4ad326
Timestamp: 1705416446 Timestamp [UCT]: 2024-01-16 14:47:26 Age [y:d:h:m:s]: 01:290:19:26:32
Block: 936634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466656 RingCT/type: yes/0
Extra: 01b440e6b4fde6bc1f6d8bd804619f88d68c8a8a52ceec8da4bb7a914afc4ad32602110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05d43bc47c6f0f679233700be90357c0bd09f530b13c6d733655c661bdab7cd7 0.600000000000 1394670 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": 936644, "vin": [ { "gen": { "height": 936634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05d43bc47c6f0f679233700be90357c0bd09f530b13c6d733655c661bdab7cd7" } } ], "extra": [ 1, 180, 64, 230, 180, 253, 230, 188, 31, 109, 139, 216, 4, 97, 159, 136, 214, 140, 138, 138, 82, 206, 236, 141, 164, 187, 122, 145, 74, 252, 74, 211, 38, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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