Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cc3fc02219b4c28de0e430abd3bfcd6d27981420a43f7c18a711657633e8935

Tx prefix hash: 3016bd187489c7d8697a52c57f4fb410a4f60b89cfbf4d7b29aa63f8ed0eac22
Tx public key: c3a0fe2108273b5abebd2b734ce3f729128ae58d4ab7249a0c696fea82f464f9
Timestamp: 1732147892 Timestamp [UCT]: 2024-11-21 00:11:32 Age [y:d:h:m:s]: 00:003:10:46:22
Block: 1158169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2469 RingCT/type: yes/0
Extra: 01c3a0fe2108273b5abebd2b734ce3f729128ae58d4ab7249a0c696fea82f464f90211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 334a8a08e27ad143e8b470f817ff2da473da3498b0de1dfff28c7fc61599e4b3 0.600000000000 1643798 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": 1158179, "vin": [ { "gen": { "height": 1158169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "334a8a08e27ad143e8b470f817ff2da473da3498b0de1dfff28c7fc61599e4b3" } } ], "extra": [ 1, 195, 160, 254, 33, 8, 39, 59, 90, 190, 189, 43, 115, 76, 227, 247, 41, 18, 138, 229, 141, 74, 183, 36, 154, 12, 105, 111, 234, 130, 244, 100, 249, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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