Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48686d852812b8e287079ce98c0092be66d7f02aebde788655936cc7e3ae92a2

Tx prefix hash: d7ef6536068fae4e5169f6e1266b457bb3d32c3b7e2b884f1fb00522df1a7948
Tx public key: 794997a7f1c9aac52ae25b4ddd83eadbf841de89f8a38bcb030be0171d2980f4
Timestamp: 1749565703 Timestamp [UCT]: 2025-06-10 14:28:23 Age [y:d:h:m:s]: 00:151:01:53:39
Block: 1302115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105651 RingCT/type: yes/0
Extra: 01794997a7f1c9aac52ae25b4ddd83eadbf841de89f8a38bcb030be0171d2980f40211000000062609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e851ebfbd5321b86df5ed77f470e168d93b7a75e75c6b59399e3617bf6a10082 0.600000000000 1789684 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": 1302125, "vin": [ { "gen": { "height": 1302115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e851ebfbd5321b86df5ed77f470e168d93b7a75e75c6b59399e3617bf6a10082" } } ], "extra": [ 1, 121, 73, 151, 167, 241, 201, 170, 197, 42, 226, 91, 77, 221, 131, 234, 219, 248, 65, 222, 137, 248, 163, 139, 203, 3, 11, 224, 23, 29, 41, 128, 244, 2, 17, 0, 0, 0, 6, 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