Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2fef3d2bf8d817864038837ba0dd62a160a114c0cf2b05180921b6397546fba

Tx prefix hash: c14153e1823599ab33bab06b443979a9591e12fbc42cad1010a4d3ad7bde269d
Tx public key: 840f0496e852349c626f0e0561a1d4571f93082bc4aa603875f0a0e753480386
Timestamp: 1749315366 Timestamp [UCT]: 2025-06-07 16:56:06 Age [y:d:h:m:s]: 00:156:02:50:59
Block: 1300052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109246 RingCT/type: yes/0
Extra: 01840f0496e852349c626f0e0561a1d4571f93082bc4aa603875f0a0e753480386021100000009bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a6f01d3e8adf350a7c4ef496cc0b0f9d302933ad46a54cd2bbfbb91c319626b 0.600000000000 1787597 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": 1300062, "vin": [ { "gen": { "height": 1300052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a6f01d3e8adf350a7c4ef496cc0b0f9d302933ad46a54cd2bbfbb91c319626b" } } ], "extra": [ 1, 132, 15, 4, 150, 232, 82, 52, 156, 98, 111, 14, 5, 97, 161, 212, 87, 31, 147, 8, 43, 196, 170, 96, 56, 117, 240, 160, 231, 83, 72, 3, 134, 2, 17, 0, 0, 0, 9, 191, 81, 178, 162, 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