Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f4e926c54b05504893659e7e06d3bc9514ecf96955c053de015f419e0ca28d7

Tx prefix hash: 3a1b2f6305a5e3b04964d883f7aface59507b16271501aeccd94cbf2698f90cf
Tx public key: 9c6ec8cddcf8a12bf7d7a7335b9f775b0c6ab8298cb0e0eda79ba99887781fb1
Timestamp: 1753073658 Timestamp [UCT]: 2025-07-21 04:54:18 Age [y:d:h:m:s]: 00:076:14:22:24
Block: 1330001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53498 RingCT/type: yes/0
Extra: 019c6ec8cddcf8a12bf7d7a7335b9f775b0c6ab8298cb0e0eda79ba99887781fb10211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96f9f1445e25d069be8d3351023c3c54b34806bf5110b77d0d0067107b985e91 0.600000000000 1817792 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": 1330011, "vin": [ { "gen": { "height": 1330001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96f9f1445e25d069be8d3351023c3c54b34806bf5110b77d0d0067107b985e91" } } ], "extra": [ 1, 156, 110, 200, 205, 220, 248, 161, 43, 247, 215, 167, 51, 91, 159, 119, 91, 12, 106, 184, 41, 140, 176, 224, 237, 167, 155, 169, 152, 135, 120, 31, 177, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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