Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c0dc1dfb14bdcde598b799b40d4ec300ea4f3113649afb4c1e6d164d137d468

Tx prefix hash: f27d8c33f0c0beeaa609aa3f7fb177b552f3b82c2a9d3d3434887c453d23b9bf
Tx public key: aca379cc2d6d237e2c53c85971ef34083115bf97e53c1d2ceae84ed8e68db5bc
Timestamp: 1702069140 Timestamp [UCT]: 2023-12-08 20:59:00 Age [y:d:h:m:s]: 01:346:18:06:38
Block: 908899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506701 RingCT/type: yes/0
Extra: 01aca379cc2d6d237e2c53c85971ef34083115bf97e53c1d2ceae84ed8e68db5bc02110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fecae376fdd43c4455eb1493a0a9702a902a94a7e8af1dd7f80c792be096049 0.600000000000 1365958 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": 908909, "vin": [ { "gen": { "height": 908899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fecae376fdd43c4455eb1493a0a9702a902a94a7e8af1dd7f80c792be096049" } } ], "extra": [ 1, 172, 163, 121, 204, 45, 109, 35, 126, 44, 83, 200, 89, 113, 239, 52, 8, 49, 21, 191, 151, 229, 60, 29, 44, 234, 232, 78, 216, 230, 141, 181, 188, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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