Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40cfa386a2cef572ff9fd2f5b8f0ece1d8108efd31dcc74ab25a97b9f43675d2

Tx prefix hash: d87b8344300f7c49b7605462edd6047dc3c8322ea268d29355cfb7a2829a4030
Tx public key: 4c6a59ff1021ee2a201adc2ffc26783dfe3e0cdbd375f4f7258aef943ac0657a
Timestamp: 1761217975 Timestamp [UCT]: 2025-10-23 11:12:55 Age [y:d:h:m:s]: 00:070:21:53:34
Block: 1396161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50769 RingCT/type: yes/0
Extra: 014c6a59ff1021ee2a201adc2ffc26783dfe3e0cdbd375f4f7258aef943ac0657a021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4043a5d3e7f6e7ced258a6d3b46076445e15e2100f259883d4fe664dc19c0d76 0.600000000000 1884446 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": 1396171, "vin": [ { "gen": { "height": 1396161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4043a5d3e7f6e7ced258a6d3b46076445e15e2100f259883d4fe664dc19c0d76" } } ], "extra": [ 1, 76, 106, 89, 255, 16, 33, 238, 42, 32, 26, 220, 47, 252, 38, 120, 61, 254, 62, 12, 219, 211, 117, 244, 247, 37, 138, 239, 148, 58, 192, 101, 122, 2, 17, 0, 0, 0, 2, 228, 220, 144, 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