Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bea50e2006bc53cdadde0a72b3bafdb611fed46c17d13318677e9055f2e82fe

Tx prefix hash: a0f8706735fc5137d7568214ef6e238adcd292c6f8822c6527e503a085c694d7
Tx public key: d3a754c1fa7a23ab3262c91bd2c81c6d9b21dab3f6b983f8346796f87536bfb2
Timestamp: 1732689327 Timestamp [UCT]: 2024-11-27 06:35:27 Age [y:d:h:m:s]: 00:124:22:41:25
Block: 1162657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89105 RingCT/type: yes/0
Extra: 01d3a754c1fa7a23ab3262c91bd2c81c6d9b21dab3f6b983f8346796f87536bfb20211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8d7c378ae52dfbf4ea634b0d718473f86db5924d33c1990f5ab9fd051981704 0.600000000000 1648314 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": 1162667, "vin": [ { "gen": { "height": 1162657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8d7c378ae52dfbf4ea634b0d718473f86db5924d33c1990f5ab9fd051981704" } } ], "extra": [ 1, 211, 167, 84, 193, 250, 122, 35, 171, 50, 98, 201, 27, 210, 200, 28, 109, 155, 33, 218, 179, 246, 185, 131, 248, 52, 103, 150, 248, 117, 54, 191, 178, 2, 17, 0, 0, 0, 1, 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