Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ddd631b4571f4e652c251530505c4bd234e1ef2efa5db4c8b109f0c41a86721

Tx prefix hash: 9b9982cff08fef4097da5cf39b8f8903e3b69e7e8bbbff9a09894747bfe036ea
Tx public key: b222bc2faf70bdb7df960dd9cf286e9e09acc36257e45eda87872d07047934ea
Timestamp: 1702440153 Timestamp [UCT]: 2023-12-13 04:02:33 Age [y:d:h:m:s]: 01:180:03:27:12
Block: 911994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389915 RingCT/type: yes/0
Extra: 01b222bc2faf70bdb7df960dd9cf286e9e09acc36257e45eda87872d07047934ea021100000004faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b52ffd40de0c29b8c24f58f0eb5ae1b89b99dca6b58949babf93da76debfb5a9 0.600000000000 1369212 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": 912004, "vin": [ { "gen": { "height": 911994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b52ffd40de0c29b8c24f58f0eb5ae1b89b99dca6b58949babf93da76debfb5a9" } } ], "extra": [ 1, 178, 34, 188, 47, 175, 112, 189, 183, 223, 150, 13, 217, 207, 40, 110, 158, 9, 172, 195, 98, 87, 228, 94, 218, 135, 135, 45, 7, 4, 121, 52, 234, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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