Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa70afca6ff54607ff43c97a2eb80d3e5a2f89dffb6bfee934ac8bdce6f9a462

Tx prefix hash: 2b7ec5516b8b6fffcceff99c1d503505f717e8c7f84a3eb3e8351d87bde7b17c
Tx public key: ff17f091f7cdb1c0e1b9960bc8d6a4e1e59108699a5430a761884fe32f79f2af
Timestamp: 1709864207 Timestamp [UCT]: 2024-03-08 02:16:47 Age [y:d:h:m:s]: 01:030:18:53:47
Block: 973528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282981 RingCT/type: yes/0
Extra: 01ff17f091f7cdb1c0e1b9960bc8d6a4e1e59108699a5430a761884fe32f79f2af02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bf34f58dbf7e94337fce5af8ab1d769ace8361dfde9d1ecdcc956989840b53d 0.600000000000 1433463 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": 973538, "vin": [ { "gen": { "height": 973528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bf34f58dbf7e94337fce5af8ab1d769ace8361dfde9d1ecdcc956989840b53d" } } ], "extra": [ 1, 255, 23, 240, 145, 247, 205, 177, 192, 225, 185, 150, 11, 200, 214, 164, 225, 229, 145, 8, 105, 154, 84, 48, 167, 97, 136, 79, 227, 47, 121, 242, 175, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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