Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 992d741e06f5cd6808b83441f7197457c430f5f739015feab4b445a2b5da4974

Tx prefix hash: d7fac6c736977a05534cdfb70a5e6fffc3d28e5469e81218bcebaae2fb4e18b6
Tx public key: aa8b451577f2323866c9b25891c20e580258937ce8be435f45a8570caa806acc
Timestamp: 1746787660 Timestamp [UCT]: 2025-05-09 10:47:40 Age [y:d:h:m:s]: 00:151:15:00:45
Block: 1279097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106024 RingCT/type: yes/0
Extra: 01aa8b451577f2323866c9b25891c20e580258937ce8be435f45a8570caa806acc0211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a43460a8263d374f6089a4fadd30b8afc23570e0eecd7c3f3a818a714472d829 0.600000000000 1766470 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": 1279107, "vin": [ { "gen": { "height": 1279097 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a43460a8263d374f6089a4fadd30b8afc23570e0eecd7c3f3a818a714472d829" } } ], "extra": [ 1, 170, 139, 69, 21, 119, 242, 50, 56, 102, 201, 178, 88, 145, 194, 14, 88, 2, 88, 147, 124, 232, 190, 67, 95, 69, 168, 87, 12, 170, 128, 106, 204, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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