Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2f43106261eaded2fbcfef8f7f7be0fb3cd56d7f83eee0d074abd5c11de60ca

Tx prefix hash: ccd99f898a4a211c5927f435d11b7aa3e28f694a27462defab928b29ae4f72da
Tx public key: 96748af4d696a55f1d7f4d0ccbfc169e92f934a504e010a6833e1231855b8a35
Timestamp: 1718006015 Timestamp [UCT]: 2024-06-10 07:53:35 Age [y:d:h:m:s]: 00:143:07:36:11
Block: 1041029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102573 RingCT/type: yes/0
Extra: 0196748af4d696a55f1d7f4d0ccbfc169e92f934a504e010a6833e1231855b8a350211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32043fa5f94f8c6f613c35d42f49de505c89b2d9c4e65756c154e314eafe34b0 0.600000000000 1509694 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": 1041039, "vin": [ { "gen": { "height": 1041029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32043fa5f94f8c6f613c35d42f49de505c89b2d9c4e65756c154e314eafe34b0" } } ], "extra": [ 1, 150, 116, 138, 244, 214, 150, 165, 95, 29, 127, 77, 12, 203, 252, 22, 158, 146, 249, 52, 165, 4, 224, 16, 166, 131, 62, 18, 49, 133, 91, 138, 53, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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