Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e55e26044b7912a6bacf3aa0d2cf351c0a11f30e921b3aaacd3e8e6119b171fc

Tx prefix hash: a83d3bdc49e08b97e61f3493db29c75bb92c084a0fe4f550ed93e7e3c7180946
Tx public key: d211b392b1cb0d464079de9cd0d048c1dc9c19cde99011cc9dd3ca5b325f1600
Timestamp: 1698208242 Timestamp [UCT]: 2023-10-25 04:30:42 Age [y:d:h:m:s]: 01:090:00:30:03
Block: 877107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325516 RingCT/type: yes/0
Extra: 01d211b392b1cb0d464079de9cd0d048c1dc9c19cde99011cc9dd3ca5b325f1600021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.761693802000 dcy

stealth address amount amount idx
00: dd091f8cd106548d6a3bfb95902902a2746c66465cab82b560eed3bd6de25089 0.761693802000 1332467 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": 877117, "vin": [ { "gen": { "height": 877107 } } ], "vout": [ { "amount": 761693802, "target": { "key": "dd091f8cd106548d6a3bfb95902902a2746c66465cab82b560eed3bd6de25089" } } ], "extra": [ 1, 210, 17, 179, 146, 177, 203, 13, 70, 64, 121, 222, 156, 208, 208, 72, 193, 220, 156, 25, 205, 233, 144, 17, 204, 157, 211, 202, 91, 50, 95, 22, 0, 2, 17, 0, 0, 0, 2, 230, 210, 127, 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