Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32e4d0885091f8ac1f6c8b615c656502c0c42fb6217e56229ab79188b135bb5d

Tx prefix hash: 90544bfe365619b53ea3786ae2c26ab36ffed12ab2a64347457d545d44e77665
Tx public key: 4fa4c9e80c67b2aed58b3f25fe9c18db8beff91b1187e87fa50b0289570ea29a
Timestamp: 1732679032 Timestamp [UCT]: 2024-11-27 03:43:52 Age [y:d:h:m:s]: 00:117:19:04:44
Block: 1162567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83993 RingCT/type: yes/0
Extra: 014fa4c9e80c67b2aed58b3f25fe9c18db8beff91b1187e87fa50b0289570ea29a0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f26ea4d76f3e56fd2330275928e9668e1a69f3229db00162349534a68972ae5 0.600000000000 1648224 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": 1162577, "vin": [ { "gen": { "height": 1162567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f26ea4d76f3e56fd2330275928e9668e1a69f3229db00162349534a68972ae5" } } ], "extra": [ 1, 79, 164, 201, 232, 12, 103, 178, 174, 213, 139, 63, 37, 254, 156, 24, 219, 139, 239, 249, 27, 17, 135, 232, 127, 165, 11, 2, 137, 87, 14, 162, 154, 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