Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76edc3a5a364c95aa53861f71a4da6bbffe11856c9ab7e35ec49c2b0b1696654

Tx prefix hash: ba83bd9796fb03c6a4c00a4d60eeee86bdec44f75618e024b7f9bbdc906ceba2
Tx public key: 01a9e9643faca29a5ae0e72b578ff111dd071344c1f501f68f3691eed16dc77c
Timestamp: 1710057704 Timestamp [UCT]: 2024-03-10 08:01:44 Age [y:d:h:m:s]: 01:037:14:47:03
Block: 975140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287871 RingCT/type: yes/0
Extra: 0101a9e9643faca29a5ae0e72b578ff111dd071344c1f501f68f3691eed16dc77c0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7daddd9d0a013542ff54fe683548938ed7e2dd19ca6819019bb4a7c3f6f1a8d6 0.600000000000 1435111 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": 975150, "vin": [ { "gen": { "height": 975140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7daddd9d0a013542ff54fe683548938ed7e2dd19ca6819019bb4a7c3f6f1a8d6" } } ], "extra": [ 1, 1, 169, 233, 100, 63, 172, 162, 154, 90, 224, 231, 43, 87, 143, 241, 17, 221, 7, 19, 68, 193, 245, 1, 246, 143, 54, 145, 238, 209, 109, 199, 124, 2, 17, 0, 0, 0, 1, 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