Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: debade33b1ffcdb82602c50d6bf5c6fdc00b8f13fbbb0638e09f93bc341d6199

Tx prefix hash: 612e8a78f9483af2f5efe913c90d8c1b38466b312bca9d6112c83c3d352dfd80
Tx public key: 3a9bb1dd7abbc8db206123ab37f29906238c32cac346c719452604f2a10d98c7
Timestamp: 1721668600 Timestamp [UCT]: 2024-07-22 17:16:40 Age [y:d:h:m:s]: 00:262:09:49:29
Block: 1071374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187482 RingCT/type: yes/0
Extra: 013a9bb1dd7abbc8db206123ab37f29906238c32cac346c719452604f2a10d98c7021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6190924a2a7ada58bb8d8ba3f278787fcf275bc572cf65315121c905e095c08 0.600000000000 1543583 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": 1071384, "vin": [ { "gen": { "height": 1071374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6190924a2a7ada58bb8d8ba3f278787fcf275bc572cf65315121c905e095c08" } } ], "extra": [ 1, 58, 155, 177, 221, 122, 187, 200, 219, 32, 97, 35, 171, 55, 242, 153, 6, 35, 140, 50, 202, 195, 70, 199, 25, 69, 38, 4, 242, 161, 13, 152, 199, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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