Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f60d3e5058a10ec240910d0b90422435adf514f0039b7856c159a964748219f1

Tx prefix hash: 4f06daf95f86759e8fa8ef0e10ca5512329b0ef79329bad91107529f3f39a765
Tx public key: 0d32e8e1df4574a516f8b9cc675c18a9ed6eda4c6eb406b21fae40fe43d82325
Timestamp: 1712721136 Timestamp [UCT]: 2024-04-10 03:52:16 Age [y:d:h:m:s]: 01:026:19:17:48
Block: 997189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280140 RingCT/type: yes/0
Extra: 010d32e8e1df4574a516f8b9cc675c18a9ed6eda4c6eb406b21fae40fe43d82325021100000003e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4dbf72b5a3575a7c994ea6ca8ed9b835eae188bc588caf17ee83d8d47f035347 0.600000000000 1457619 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": 997199, "vin": [ { "gen": { "height": 997189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4dbf72b5a3575a7c994ea6ca8ed9b835eae188bc588caf17ee83d8d47f035347" } } ], "extra": [ 1, 13, 50, 232, 225, 223, 69, 116, 165, 22, 248, 185, 204, 103, 92, 24, 169, 237, 110, 218, 76, 110, 180, 6, 178, 31, 174, 64, 254, 67, 216, 35, 37, 2, 17, 0, 0, 0, 3, 224, 133, 50, 182, 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