Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4f0f30f79c452fa75f243674e276ac02efaf0afc59cfdf746b3786863228816

Tx prefix hash: 3f1f8d799874f3564e12cba899d8de3c6ee5a1b41a8dad4b2a7d9153a833a975
Tx public key: ede179913927f6b73f8e885327aa6329fbd897b96c077bb4dac6f0a199c4015e
Timestamp: 1726560822 Timestamp [UCT]: 2024-09-17 08:13:42 Age [y:d:h:m:s]: 01:053:13:51:33
Block: 1111949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296708 RingCT/type: yes/0
Extra: 01ede179913927f6b73f8e885327aa6329fbd897b96c077bb4dac6f0a199c4015e02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd51a9d129f8d6da06d4469fae0defd315805b688b832500cb94060a193ae52c 0.600000000000 1591090 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": 1111959, "vin": [ { "gen": { "height": 1111949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd51a9d129f8d6da06d4469fae0defd315805b688b832500cb94060a193ae52c" } } ], "extra": [ 1, 237, 225, 121, 145, 57, 39, 246, 183, 63, 142, 136, 83, 39, 170, 99, 41, 251, 216, 151, 185, 108, 7, 123, 180, 218, 198, 240, 161, 153, 196, 1, 94, 2, 17, 0, 0, 0, 3, 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