Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19d988666234880dcc7aaa290df3d7a8a6ecb1a20bd47d49d9808432ac0362af

Tx prefix hash: 96e0aef4a442cb88ffa3d0c8f9ab95e46d33e7ecc99e694bdf3d1e491f84fa02
Tx public key: d59695f69091710758084f667d5cbfa347b4517ed01d1efc9d3c8a128c5d5a54
Timestamp: 1734488236 Timestamp [UCT]: 2024-12-18 02:17:16 Age [y:d:h:m:s]: 00:097:09:12:32
Block: 1177585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69353 RingCT/type: yes/0
Extra: 01d59695f69091710758084f667d5cbfa347b4517ed01d1efc9d3c8a128c5d5a540211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4446751847d11ef73286d1e5a698e11f3778f682f99457b96e9dcb5f2ca6795 0.600000000000 1663956 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": 1177595, "vin": [ { "gen": { "height": 1177585 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4446751847d11ef73286d1e5a698e11f3778f682f99457b96e9dcb5f2ca6795" } } ], "extra": [ 1, 213, 150, 149, 246, 144, 145, 113, 7, 88, 8, 79, 102, 125, 92, 191, 163, 71, 180, 81, 126, 208, 29, 30, 252, 157, 60, 138, 18, 140, 93, 90, 84, 2, 17, 0, 0, 0, 1, 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