Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 311c7f535ceb41ef0104446516f8db9200e6313e1f31ba14ede753d1f3867fa7

Tx prefix hash: f2c7a683bb30d2f1a2bffb98513c70c3d16334b3994081b49d75f5088ee3acf6
Tx public key: cdb09523439f3e3709d19c8777877b797d9de000aa7c38cda0ac825a6dc8882c
Timestamp: 1761961092 Timestamp [UCT]: 2025-11-01 01:38:12 Age [y:d:h:m:s]: 00:004:14:04:06
Block: 1402320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3270 RingCT/type: yes/0
Extra: 01cdb09523439f3e3709d19c8777877b797d9de000aa7c38cda0ac825a6dc8882c02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 059d8684bf2ed34b30a58b0d83343ff356a8de2bd0c47dc07f5af3677ec01c13 0.600000000000 1890639 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": 1402330, "vin": [ { "gen": { "height": 1402320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "059d8684bf2ed34b30a58b0d83343ff356a8de2bd0c47dc07f5af3677ec01c13" } } ], "extra": [ 1, 205, 176, 149, 35, 67, 159, 62, 55, 9, 209, 156, 135, 119, 135, 123, 121, 125, 157, 224, 0, 170, 124, 56, 205, 160, 172, 130, 90, 109, 200, 136, 44, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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