Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f28147a014180fb33498541129812e31f659697b89f01467e29bb45ff1ed036b

Tx prefix hash: 8480f22c986529a1e1714d9e8098ffeb3abfe9d7529d0b2b7ac2a71044ee13c8
Tx public key: ae837ff9e68de14fe951a7d1fdee87a658d46b19f22777331b8a2a722ed6cb63
Timestamp: 1760587232 Timestamp [UCT]: 2025-10-16 04:00:32 Age [y:d:h:m:s]: 00:024:13:04:41
Block: 1390925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17578 RingCT/type: yes/0
Extra: 01ae837ff9e68de14fe951a7d1fdee87a658d46b19f22777331b8a2a722ed6cb630211000000082609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1748fbfb7ac8c1ae149ca32a8e715e0e726572bbb03faae4feb1f8bf6cfa597 0.600000000000 1879172 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": 1390935, "vin": [ { "gen": { "height": 1390925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1748fbfb7ac8c1ae149ca32a8e715e0e726572bbb03faae4feb1f8bf6cfa597" } } ], "extra": [ 1, 174, 131, 127, 249, 230, 141, 225, 79, 233, 81, 167, 209, 253, 238, 135, 166, 88, 212, 107, 25, 242, 39, 119, 51, 27, 138, 42, 114, 46, 214, 203, 99, 2, 17, 0, 0, 0, 8, 38, 9, 179, 160, 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