Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c80c0ff233394d5b378488cdecae1096bdd7479bbbb42a7d4bed4830bc626073

Tx prefix hash: f12a764cd57958749c3f4c3457d46768d9479dd4dcf59630ab63b67a2c640b7f
Tx public key: 26b5afc5a2e61d6f4aaf62d8577556b4011e0f63813ac87550d60ff893cee1b6
Timestamp: 1710060342 Timestamp [UCT]: 2024-03-10 08:45:42 Age [y:d:h:m:s]: 01:240:21:09:57
Block: 975163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430849 RingCT/type: yes/0
Extra: 0126b5afc5a2e61d6f4aaf62d8577556b4011e0f63813ac87550d60ff893cee1b60211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 388e99cbe41d34e47f9bb40c509b6a65d8c4fa53b9cb6a0cd2f75f41f0cd760e 0.600000000000 1435134 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": 975173, "vin": [ { "gen": { "height": 975163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "388e99cbe41d34e47f9bb40c509b6a65d8c4fa53b9cb6a0cd2f75f41f0cd760e" } } ], "extra": [ 1, 38, 181, 175, 197, 162, 230, 29, 111, 74, 175, 98, 216, 87, 117, 86, 180, 1, 30, 15, 99, 129, 58, 200, 117, 80, 214, 15, 248, 147, 206, 225, 182, 2, 17, 0, 0, 0, 8, 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