Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8288f7dfd292240c605736234772e1acdc52eda61b8be3c4fa814d868f968a7b

Tx prefix hash: 6572711ad7d290613ed7aca3d4d6d493c953bb882ac82761d61e15cdb96b371c
Tx public key: eab17a2b7c439fe70d844fb869f269718e6be825295bf40375e8d0ee6bd48070
Timestamp: 1697024092 Timestamp [UCT]: 2023-10-11 11:34:52 Age [y:d:h:m:s]: 01:225:18:09:18
Block: 867282 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422422 RingCT/type: yes/0
Extra: 01eab17a2b7c439fe70d844fb869f269718e6be825295bf40375e8d0ee6bd480700211000000034b8f5122000000000000000000

1 output(s) for total of 0.820984087000 dcy

stealth address amount amount idx
00: 9ea11226afee208f25758dc14da5b8af6c8b2bd00c2661a1f7b263a8ebcad59e 0.820984087000 1321956 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": 867292, "vin": [ { "gen": { "height": 867282 } } ], "vout": [ { "amount": 820984087, "target": { "key": "9ea11226afee208f25758dc14da5b8af6c8b2bd00c2661a1f7b263a8ebcad59e" } } ], "extra": [ 1, 234, 177, 122, 43, 124, 67, 159, 231, 13, 132, 79, 184, 105, 242, 105, 113, 142, 107, 232, 37, 41, 91, 244, 3, 117, 232, 208, 238, 107, 212, 128, 112, 2, 17, 0, 0, 0, 3, 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