Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 707c115270d0c0c8430dd5df77d9d7bb33a595eb1a50b25b5ca6c1572d412e67

Tx prefix hash: e52532905f37bb1a872769f1f0676df406fab15811d3ff0f3a18882c319c1cb6
Tx public key: 59692b79683e1c4501a4c9db495c0055e167be392a1fe65da43f7ae58e480e31
Timestamp: 1736598037 Timestamp [UCT]: 2025-01-11 12:20:37 Age [y:d:h:m:s]: 00:096:11:39:00
Block: 1195015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68741 RingCT/type: yes/0
Extra: 0159692b79683e1c4501a4c9db495c0055e167be392a1fe65da43f7ae58e480e310211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca9d7170b8960cf5496c4b2db1700a732ee40a730dad8ffca413ea5733d04263 0.600000000000 1681600 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": 1195025, "vin": [ { "gen": { "height": 1195015 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca9d7170b8960cf5496c4b2db1700a732ee40a730dad8ffca413ea5733d04263" } } ], "extra": [ 1, 89, 105, 43, 121, 104, 62, 28, 69, 1, 164, 201, 219, 73, 92, 0, 85, 225, 103, 190, 57, 42, 31, 230, 93, 164, 63, 122, 229, 142, 72, 14, 49, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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