Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 054fc4a25ce27c0a89930612eca2a6d3483bf334dcecd1160b0d7914e94fa52b

Tx prefix hash: e7cec36007124e108417da500af6f3013b64db255a3c4108fccfe4c74a5f15c8
Tx public key: 40d259a096fbeb8bb7d77b2533f2f5841a86f7abb4ab11dd6ddccfc0acca76e8
Timestamp: 1751725549 Timestamp [UCT]: 2025-07-05 14:25:49 Age [y:d:h:m:s]: 00:127:13:46:24
Block: 1319305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89531 RingCT/type: yes/0
Extra: 0140d259a096fbeb8bb7d77b2533f2f5841a86f7abb4ab11dd6ddccfc0acca76e802110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 534bc80a78143a43743f3b8f4ef5d1a7c3cd9fa7309e9fda764bf36b7075c7cb 0.600000000000 1806996 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": 1319315, "vin": [ { "gen": { "height": 1319305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "534bc80a78143a43743f3b8f4ef5d1a7c3cd9fa7309e9fda764bf36b7075c7cb" } } ], "extra": [ 1, 64, 210, 89, 160, 150, 251, 235, 139, 183, 215, 123, 37, 51, 242, 245, 132, 26, 134, 247, 171, 180, 171, 17, 221, 109, 220, 207, 192, 172, 202, 118, 232, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 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