Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3955530c7071cd7498032207f791a65b189b9cb8154e0fafa39d4e48cce45a64

Tx prefix hash: e0040f63f5d4dab816aade96f8872f1e3abea4ed21821438039d816faf50cef5
Tx public key: 98d8ada7b7a75cd97bd67336c82b33bd418ce1ddb2f6f2af9ecfd8c0260e0dfb
Timestamp: 1697332373 Timestamp [UCT]: 2023-10-15 01:12:53 Age [y:d:h:m:s]: 01:076:16:27:00
Block: 869828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316046 RingCT/type: yes/0
Extra: 0198d8ada7b7a75cd97bd67336c82b33bd418ce1ddb2f6f2af9ecfd8c0260e0dfb02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.805190757000 dcy

stealth address amount amount idx
00: 0f21903219b3a19b86316eb2dd802d7a6fc3a08ad4b2150dc21191f8a0c7c126 0.805190757000 1324687 of 0

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": 869838, "vin": [ { "gen": { "height": 869828 } } ], "vout": [ { "amount": 805190757, "target": { "key": "0f21903219b3a19b86316eb2dd802d7a6fc3a08ad4b2150dc21191f8a0c7c126" } } ], "extra": [ 1, 152, 216, 173, 167, 183, 167, 92, 217, 123, 214, 115, 54, 200, 43, 51, 189, 65, 140, 225, 221, 178, 246, 242, 175, 158, 207, 216, 192, 38, 14, 13, 251, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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