Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 935ac1d9733a050bb0a5afc439c9310f3f458ca799d33d5b693a68d3a4af6338

Tx prefix hash: eaf11a4877f6d97629831f546a21a02e26ea57ab4c0e5bbfaf1651fcb6d7bea6
Tx public key: f05fe3651bec824e92c59a337bb2acff88e496745655d8b22f2a7d06ac9db350
Timestamp: 1694072040 Timestamp [UCT]: 2023-09-07 07:34:00 Age [y:d:h:m:s]: 01:170:11:46:31
Block: 842788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382914 RingCT/type: yes/0
Extra: 01f05fe3651bec824e92c59a337bb2acff88e496745655d8b22f2a7d06ac9db3500211000000134b8f5122000000000000000000

1 output(s) for total of 0.989677200000 dcy

stealth address amount amount idx
00: 03caa6a58ec49081d8456f15a589d47acd8ff4ebf1a7f02bf08da423d8498baf 0.989677200000 1295942 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": 842798, "vin": [ { "gen": { "height": 842788 } } ], "vout": [ { "amount": 989677200, "target": { "key": "03caa6a58ec49081d8456f15a589d47acd8ff4ebf1a7f02bf08da423d8498baf" } } ], "extra": [ 1, 240, 95, 227, 101, 27, 236, 130, 78, 146, 197, 154, 51, 123, 178, 172, 255, 136, 228, 150, 116, 86, 85, 216, 178, 47, 42, 125, 6, 172, 157, 179, 80, 2, 17, 0, 0, 0, 19, 75, 143, 81, 34, 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