Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8b8c36141238b31e5f662aaac0ce669aa9ffb203fe09d1f274894c38c561a98

Tx prefix hash: 5605af653581b73e281efa40e88888ef824a0cbc919e0bf64e3d66873926d627
Tx public key: 7f88146952f8bf52e3914501e80dc97e7ac488b4706a2d6d3e9197e7829f71ff
Timestamp: 1749665852 Timestamp [UCT]: 2025-06-11 18:17:32 Age [y:d:h:m:s]: 00:157:10:09:24
Block: 1302925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110214 RingCT/type: yes/0
Extra: 017f88146952f8bf52e3914501e80dc97e7ac488b4706a2d6d3e9197e7829f71ff021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d82ccece7aef1f9f46be39be34012297220e6be2cc76ffec2ce4e0c609e90ea4 0.600000000000 1790500 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": 1302935, "vin": [ { "gen": { "height": 1302925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d82ccece7aef1f9f46be39be34012297220e6be2cc76ffec2ce4e0c609e90ea4" } } ], "extra": [ 1, 127, 136, 20, 105, 82, 248, 191, 82, 227, 145, 69, 1, 232, 13, 201, 126, 122, 196, 136, 180, 112, 106, 45, 109, 62, 145, 151, 231, 130, 159, 113, 255, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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