Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71f5453724f19f514b285b968fc1a1b061f6be81bea585e1eab42e63338b9204

Tx prefix hash: 3f6be9a64f5f68a00eea68c2213fcfb394a8bcda2b6d23a3108d8182d479ccbb
Tx public key: 4ebc498ad557dba50e57d9d13fb370ca92c0e0431d665f4d7def4dff9280a1c5
Timestamp: 1713789414 Timestamp [UCT]: 2024-04-22 12:36:54 Age [y:d:h:m:s]: 00:206:14:32:23
Block: 1006062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147897 RingCT/type: yes/0
Extra: 014ebc498ad557dba50e57d9d13fb370ca92c0e0431d665f4d7def4dff9280a1c502110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2941a83622bc19549d937bc2e0cb24b5b3d62dd4c739bc8089b35d4660ac1142 0.600000000000 1466966 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": 1006072, "vin": [ { "gen": { "height": 1006062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2941a83622bc19549d937bc2e0cb24b5b3d62dd4c739bc8089b35d4660ac1142" } } ], "extra": [ 1, 78, 188, 73, 138, 213, 87, 219, 165, 14, 87, 217, 209, 63, 179, 112, 202, 146, 192, 224, 67, 29, 102, 95, 77, 125, 239, 77, 255, 146, 128, 161, 197, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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