Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 708e13ae26f5daa42ef546243933a293a43675a584b9136204a3267eab19cd6f

Tx prefix hash: 10d6c9e6affcb6660aa4b275216aa802d9e55b38638dc2687b31246cdfe3f882
Tx public key: b23df5e6028bedcc29902bd54f11ab3882c7b59f89a566328c0610eb3d1d2775
Timestamp: 1734631947 Timestamp [UCT]: 2024-12-19 18:12:27 Age [y:d:h:m:s]: 00:107:15:52:47
Block: 1178768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76719 RingCT/type: yes/0
Extra: 01b23df5e6028bedcc29902bd54f11ab3882c7b59f89a566328c0610eb3d1d2775021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e120640e0d6fbd33e44c550bf0cc1e07a34f41f346e3f2bd251cfb8cd88833ac 0.600000000000 1665157 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": 1178778, "vin": [ { "gen": { "height": 1178768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e120640e0d6fbd33e44c550bf0cc1e07a34f41f346e3f2bd251cfb8cd88833ac" } } ], "extra": [ 1, 178, 61, 245, 230, 2, 139, 237, 204, 41, 144, 43, 213, 79, 17, 171, 56, 130, 199, 181, 159, 137, 165, 102, 50, 140, 6, 16, 235, 61, 29, 39, 117, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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