Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34d44cd02201dad270f6203906c5f606f5c3dbe35c92ef9427931f0d68fce39a

Tx prefix hash: 3d0d6adb3f705c108b0d7a1210a3d720d290c76c7aed7aeaed8c2e80d708a7a5
Tx public key: f7596cf8f3f7e12e541c7a95ca653562886484d948444b52ddd19753245d910f
Timestamp: 1713385107 Timestamp [UCT]: 2024-04-17 20:18:27 Age [y:d:h:m:s]: 00:157:02:58:35
Block: 1002714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112550 RingCT/type: yes/0
Extra: 01f7596cf8f3f7e12e541c7a95ca653562886484d948444b52ddd19753245d910f0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b788b7bf950d3754bef5d8e7f9f6c537d8c7300e03b1cee047aacf293b19da2 0.600000000000 1463234 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": 1002724, "vin": [ { "gen": { "height": 1002714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b788b7bf950d3754bef5d8e7f9f6c537d8c7300e03b1cee047aacf293b19da2" } } ], "extra": [ 1, 247, 89, 108, 248, 243, 247, 225, 46, 84, 28, 122, 149, 202, 101, 53, 98, 136, 100, 132, 217, 72, 68, 75, 82, 221, 209, 151, 83, 36, 93, 145, 15, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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