Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 347bebfdfa65fa3d49ed8df779a71ce08f443d62692a0c14a05d5383eb9616a0

Tx prefix hash: 9561d9e676a1ce0ff5477ef0a2c94620c6ef285f7edde8961e7f0b86a5aa5b22
Tx public key: ac15928e399b7d184ac111c79f8cf0d4efb497f31a1e130a30063b6ecb5a17c6
Timestamp: 1764165596 Timestamp [UCT]: 2025-11-26 13:59:56 Age [y:d:h:m:s]: 00:000:20:30:54
Block: 1420580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 617 RingCT/type: yes/0
Extra: 01ac15928e399b7d184ac111c79f8cf0d4efb497f31a1e130a30063b6ecb5a17c60211000000024e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0015bcc72e4c2799355ea34067d3a35ce24a843ab5f5093bf1ca4168bb1536e 0.600000000000 1909127 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": 1420590, "vin": [ { "gen": { "height": 1420580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0015bcc72e4c2799355ea34067d3a35ce24a843ab5f5093bf1ca4168bb1536e" } } ], "extra": [ 1, 172, 21, 146, 142, 57, 155, 125, 24, 74, 193, 17, 199, 159, 140, 240, 212, 239, 180, 151, 243, 26, 30, 19, 10, 48, 6, 59, 110, 203, 90, 23, 198, 2, 17, 0, 0, 0, 2, 78, 123, 252, 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