Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89b58779f052a4c09a62595d640ca895d49f58729c609aae965d8c19dccad9f4

Tx prefix hash: 953961ff058fdf1f7bb496bb9b4a3a69d39efb56bb4b01c94606a345e59b4bb8
Tx public key: 378ecd354111b501cb6f7be2672af034dccacc8d7a46b375b4fe6f2ffa8de106
Timestamp: 1701626162 Timestamp [UCT]: 2023-12-03 17:56:02 Age [y:d:h:m:s]: 01:125:02:46:01
Block: 905223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350562 RingCT/type: yes/0
Extra: 01378ecd354111b501cb6f7be2672af034dccacc8d7a46b375b4fe6f2ffa8de106021100000001e08532b6000000000000000000

1 output(s) for total of 0.614639407000 dcy

stealth address amount amount idx
00: 04c32220ba33ac12844e9a10d553da16bda304124162d1bef9593566931a8bf8 0.614639407000 1362098 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": 905233, "vin": [ { "gen": { "height": 905223 } } ], "vout": [ { "amount": 614639407, "target": { "key": "04c32220ba33ac12844e9a10d553da16bda304124162d1bef9593566931a8bf8" } } ], "extra": [ 1, 55, 142, 205, 53, 65, 17, 181, 1, 203, 111, 123, 226, 103, 42, 240, 52, 220, 202, 204, 141, 122, 70, 179, 117, 180, 254, 111, 47, 250, 141, 225, 6, 2, 17, 0, 0, 0, 1, 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