Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0167c65cc06d098fdf7278b7a5e880dc62e76d4269666fe1e4e0c751096d43b

Tx prefix hash: 9a05bb6585d68b85c6e95cebc85ac095528f0eacc5829f67504e3850469274bb
Tx public key: 0d59c08fe7a0b6f33fcb5bd5e767dace9b556a688f3db12e22882b9cc199329f
Timestamp: 1712872715 Timestamp [UCT]: 2024-04-11 21:58:35 Age [y:d:h:m:s]: 00:320:02:07:57
Block: 998443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228833 RingCT/type: yes/0
Extra: 010d59c08fe7a0b6f33fcb5bd5e767dace9b556a688f3db12e22882b9cc199329f02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4a80bd0b26fac9656f7d4384003c1848aac69f6e6f9786c5f300deb0dc1c2f3 0.600000000000 1458893 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": 998453, "vin": [ { "gen": { "height": 998443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4a80bd0b26fac9656f7d4384003c1848aac69f6e6f9786c5f300deb0dc1c2f3" } } ], "extra": [ 1, 13, 89, 192, 143, 231, 160, 182, 243, 63, 203, 91, 213, 231, 103, 218, 206, 155, 85, 106, 104, 143, 61, 177, 46, 34, 136, 43, 156, 193, 153, 50, 159, 2, 17, 0, 0, 0, 4, 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