Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73abab70e119d325120ae6eba42c65bfa46eb787ad40ba811fe5330ef7c7ab1e

Tx prefix hash: 96233641f745f24a7ca9261c3cc78d76f9397f13568c351696ff246e45ab7b1d
Tx public key: 70d95c88fc9ae5e14f2bca033b2e72b937e096632ca5f8c5c85f0388a3b26792
Timestamp: 1736704066 Timestamp [UCT]: 2025-01-12 17:47:46 Age [y:d:h:m:s]: 00:156:22:02:37
Block: 1195901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111857 RingCT/type: yes/0
Extra: 0170d95c88fc9ae5e14f2bca033b2e72b937e096632ca5f8c5c85f0388a3b267920211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bc6d0f3d545923d78b9c51970fa58b6480568bf2bc811c4baee77d0642a556d 0.600000000000 1682494 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": 1195911, "vin": [ { "gen": { "height": 1195901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bc6d0f3d545923d78b9c51970fa58b6480568bf2bc811c4baee77d0642a556d" } } ], "extra": [ 1, 112, 217, 92, 136, 252, 154, 229, 225, 79, 43, 202, 3, 59, 46, 114, 185, 55, 224, 150, 99, 44, 165, 248, 197, 200, 95, 3, 136, 163, 178, 103, 146, 2, 17, 0, 0, 0, 7, 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