Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08a4ee4f53dfcecbdca911cd17819e6a629c6bf2f1a72e1f140a1d3e4167b5ef

Tx prefix hash: b53c98e3c89c0f90d11c919915c25561ebecdee74abc8075309aeff4f846e064
Tx public key: 47e82f6eee5b807cd9b536297586d9254702de1ea42ec3cdf802f6dc07fdec2d
Timestamp: 1733384459 Timestamp [UCT]: 2024-12-05 07:40:59 Age [y:d:h:m:s]: 00:148:18:13:48
Block: 1168414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106137 RingCT/type: yes/0
Extra: 0147e82f6eee5b807cd9b536297586d9254702de1ea42ec3cdf802f6dc07fdec2d021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6502d497eedf356dad29bef5969e0eb73eaa6467be47064ff3b315cf1ade75e0 0.600000000000 1654123 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": 1168424, "vin": [ { "gen": { "height": 1168414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6502d497eedf356dad29bef5969e0eb73eaa6467be47064ff3b315cf1ade75e0" } } ], "extra": [ 1, 71, 232, 47, 110, 238, 91, 128, 124, 217, 181, 54, 41, 117, 134, 217, 37, 71, 2, 222, 30, 164, 46, 195, 205, 248, 2, 246, 220, 7, 253, 236, 45, 2, 17, 0, 0, 0, 4, 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