Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30e3ff9b8b17984f6d813f76b1b10938b9f8f5929ce8613774011d2cfecf7906

Tx prefix hash: 698727b722a3ac12cd22c6912f6c2464d7695e74da2b89c9f8ae3fe9b4ba39a3
Tx public key: 0b79d13a0b11cc6c2a520dbb84e50a93ba880a1db044d8937e7963d9a130ab11
Timestamp: 1763777806 Timestamp [UCT]: 2025-11-22 02:16:46 Age [y:d:h:m:s]: 00:004:12:34:25
Block: 1417360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3244 RingCT/type: yes/0
Extra: 010b79d13a0b11cc6c2a520dbb84e50a93ba880a1db044d8937e7963d9a130ab11021100000001defb8f18000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed4c30d518af98404e66041c1ea910a628e7ca0a86574d8ba8a07cd6656099d9 0.600000000000 1905883 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": 1417370, "vin": [ { "gen": { "height": 1417360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed4c30d518af98404e66041c1ea910a628e7ca0a86574d8ba8a07cd6656099d9" } } ], "extra": [ 1, 11, 121, 209, 58, 11, 17, 204, 108, 42, 82, 13, 187, 132, 229, 10, 147, 186, 136, 10, 29, 176, 68, 216, 147, 126, 121, 99, 217, 161, 48, 171, 17, 2, 17, 0, 0, 0, 1, 222, 251, 143, 24, 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