Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad04dcb08ecfd343ff3102821e7ee65a346ade194348c02d414d39a7f6088d7b

Tx prefix hash: 69964dbbb1677ea08c415b42c38aca451c1c28cea68b4e1e39a5d6ab9ec5972d
Tx public key: bf7ed6802d31a71a223cd71187c29e470ce3b2b9855468895af91a4c608cb98d
Timestamp: 1706940361 Timestamp [UCT]: 2024-02-03 06:06:01 Age [y:d:h:m:s]: 01:118:15:08:20
Block: 949265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345903 RingCT/type: yes/0
Extra: 01bf7ed6802d31a71a223cd71187c29e470ce3b2b9855468895af91a4c608cb98d02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7d70334b15ff7a4c123e8922c0695ee55c8d0292dc69fdf985421028d38b0e7 0.600000000000 1407789 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": 949275, "vin": [ { "gen": { "height": 949265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7d70334b15ff7a4c123e8922c0695ee55c8d0292dc69fdf985421028d38b0e7" } } ], "extra": [ 1, 191, 126, 214, 128, 45, 49, 167, 26, 34, 60, 215, 17, 135, 194, 158, 71, 12, 227, 178, 185, 133, 84, 104, 137, 90, 249, 26, 76, 96, 140, 185, 141, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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