Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aebdf86a47711f497bc7db36b2732d046e5054bd583806adb2ba1a138fa239c1

Tx prefix hash: 4477d95c02671340fbe14bd321e0d79c5d7969b97a29df0e3267558d46ba9adc
Tx public key: 1d3a5af498e83d60dfd161e8d4f975483779b0c7a66bdae48c957278dd4d479c
Timestamp: 1750994286 Timestamp [UCT]: 2025-06-27 03:18:06 Age [y:d:h:m:s]: 00:144:04:49:45
Block: 1313598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101076 RingCT/type: yes/0
Extra: 011d3a5af498e83d60dfd161e8d4f975483779b0c7a66bdae48c957278dd4d479c021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac64b91ff48858ad32f9f39d3327537a879406d8dd81802b670686a2f2f5c381 0.600000000000 1801239 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": 1313608, "vin": [ { "gen": { "height": 1313598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac64b91ff48858ad32f9f39d3327537a879406d8dd81802b670686a2f2f5c381" } } ], "extra": [ 1, 29, 58, 90, 244, 152, 232, 61, 96, 223, 209, 97, 232, 212, 249, 117, 72, 55, 121, 176, 199, 166, 107, 218, 228, 140, 149, 114, 120, 221, 77, 71, 156, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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