Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7097e2a9266b2065bc14f80a870232f38c98dacbcdbc1e35289b52b91ca3e8ea

Tx prefix hash: bed38f11207f066a6cb99c1094c987a9a3cc0ea31a5c88948481312c20f0f99a
Tx public key: 812359a111afa5a7cf6af0dce783e7fcc49e82f6f0b0a7c00ebb9dcfeb92ce3d
Timestamp: 1734196197 Timestamp [UCT]: 2024-12-14 17:09:57 Age [y:d:h:m:s]: 00:098:16:49:00
Block: 1175150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70326 RingCT/type: yes/0
Extra: 01812359a111afa5a7cf6af0dce783e7fcc49e82f6f0b0a7c00ebb9dcfeb92ce3d021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: feb9209453aef1ef1c2a477dbb2b466b479b1ba38240ddcb32737f4f4f616c76 0.600000000000 1661389 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": 1175160, "vin": [ { "gen": { "height": 1175150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "feb9209453aef1ef1c2a477dbb2b466b479b1ba38240ddcb32737f4f4f616c76" } } ], "extra": [ 1, 129, 35, 89, 161, 17, 175, 165, 167, 207, 106, 240, 220, 231, 131, 231, 252, 196, 158, 130, 246, 240, 176, 167, 192, 14, 187, 157, 207, 235, 146, 206, 61, 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